Set whether an event is a start, intermediate, end or boundary event.
In Innovator, the event's type is normally recognized automatically based on the position of the inflowing sequence or message flows. However, there are certain circumstances where the event type needs to be manually set:
| Event Type | Criteria for Automatic Recognition |
|---|---|
| Start event | Only outflowing sequence flows |
| Inflowing or outflowing intermediate event | Both inflowing and outflowing sequence flows: direction can be automatically recognized based on message flows. If this is not the case, it needs to be set manually. |
| End event | Only inflowing sequence flows |
| Interrupting or non-interrupting subprocess start event |
In event-based subprocess, only outflowing sequence flows Is automatically created as an interrupting event; can be manually set to non-interrupting |
| Interrupting or non-interrupting boundary event |
Placed on an activity's boundary. Is automatically created as an interrupting event; can be manually set to non-interrupting |
You can normally leave the Innovator determines Type property set. This enables Innovator to adapt the event type if this is required due to further modeling. This does not influence being about to manually change the type.
The type is set and the icon is shown in the diagram accordingly.
Task/activity is highlighted.
The event is linked with the task/activity and shown as a boundary event.
The subprocess is highlighted.
The event is inserted in the subprocess.
The event is shown as non-interrupting or interrupting, depending on whether you checked or unchecked the box.
Innovator X Generation 11 R4 - Copyright © 2011-2012 - MID GmbH Nuremberg - DIN EN 9001 certified - All rights reserved.